Skip to content

Rewrite landing hero closing copy into a "so what + what's coming" hook#83

Merged
adnaan merged 1 commit into
mainfrom
adnaan/landing-hero-so-what
Jun 18, 2026
Merged

Rewrite landing hero closing copy into a "so what + what's coming" hook#83
adnaan merged 1 commit into
mainfrom
adnaan/landing-hero-so-what

Conversation

@adnaan

@adnaan adnaan commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

What

Rewrites the landing hero's closing caption (content/index.md). It previously stated only negatives — "No separate frontend, no build step, no generated code" — and never told the reader the payoff or teased the spine that follows, so the "real app, not a toy" claim (which lands one section later) went unearned.

The new copy is a two-beat block, in relatable terminology (SPA, REST API, frontend framework, progressive enhancement, real-time):

  1. The payoff the literal 20-line greet app already delivers — live in-place updates, no full reload, no JavaScript you had to write.
  2. The real-app features that are "a small diff on this exact code" — form validation, loading states, progressive enhancement, real-time cross-tab sync, multiplayer/collaborative views, file uploads — i.e. exactly what the rest of the page builds, step by step.
-    <p class="hero-cap">That's the whole app — ~20 lines of Go and standard HTML. No separate frontend, no build step, no generated code.</p>
+    <p class="hero-cap">That's the whole app — ~20 lines of Go and standard HTML. No SPA framework, no REST API, no build step.</p>
+    <p class="hero-cap">It reads like a classic server-rendered form, but it <b>behaves like a modern app</b>: the page updates live, with no full reload and no JavaScript you had to write. From here, everything you'd reach for a frontend framework to do — form validation, loading states, progressive enhancement, real-time sync across tabs, multiplayer/collaborative views, file uploads — is a <b>small diff on this exact code</b>. The rest of this page builds them, one step at a time.</p>

Accuracy note

The hero embeds the storeless examples/greet (state re-cloned to initial on every fresh request), so "works without JavaScript" is deliberately kept in the diff-away bucket as "progressive enhancement" — the bare 20 lines submit a plain POST but render the default; persisting across a no-JS round-trip needs the separate greet-nojs store. No claim is made that the literal hero app works identically with JS off.

Verification

  • tinkerdown validate content/ — 93/93 pages, 0 errors
  • chromedp render check against the prod Docker image: all new copy renders, old caption gone, greet embed still mounts (visually confirmed)
  • GOWORK=off go test ./cmd/... ./examples/... green

🤖 Generated with Claude Code

The hero's closing caption only stated negatives ("no separate frontend,
no build step, no generated code") and never told the reader the payoff or
teased the spine that follows, so the "real, not a toy" claim went unearned.

Replace it with a two-beat block in relatable terminology (SPA, REST API,
frontend framework, progressive enhancement, real-time): first the payoff
the literal 20-line greet app already delivers (live in-place updates, no
reload, no JavaScript written), then the real-app features that are "a small
diff on this exact code" — validation, loading, progressive enhancement,
cross-tab sync, multi-user, uploads — which are exactly what the rest of the
page builds. Progressive enhancement stays in the "diff away" bucket since
the storeless hero greet doesn't persist across a no-JS POST.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@adnaan adnaan merged commit 4bddd68 into main Jun 18, 2026
3 checks passed
@adnaan adnaan deleted the adnaan/landing-hero-so-what branch June 18, 2026 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant